System and method for trailer height adjustment

ABSTRACT

A vehicle system comprises a hitch assembly mounted on a vehicle, a display, and a controller. The controller is configured to access a saved configuration for the hitch assembly and display the saved configuration on the display. The controller is further configured to receive a selection of the saved configuration and program a characteristic of the hitch assembly based on the selection.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to a system for assisting in avehicle-trailer hitching operation. In particular, the present systemrelates to a system and method configured to program or detect acoupling interface for a vehicle-trailer combination.

BACKGROUND OF THE DISCLOSURE

Hitching a trailer to a vehicle can be a difficult and time-consumingexperience. In particular, aligning a vehicle hitch ball with thedesired trailer hitch can, depending on the initial location of thetrailer relative to the vehicle, require repeated forward and reversedriving coordinated with multiple steering maneuvers to appropriatelyposition the vehicle. Further, through a significant portion of thedriving needed for appropriate hitch ball alignment, the trailer hitchcannot be seen, and the hitch ball can, under ordinary circumstances,never actually be seen by the driver. This lack of sight lines requiresinference of the positioning of the hitch ball and hitch based onexperience with a particular vehicle and trailer, and can still requiremultiple instances of stopping and stepping out of the vehicle toconfirm alignment or to note an appropriate correction for a subsequentset of maneuvers. Even further, the closeness of the hitch ball to therear bumper of the vehicle means that any overshoot can cause acollision of the vehicle with the trailer. Accordingly, furtheradvancements may be desired.

SUMMARY OF THE DISCLOSURE

According to one aspect of the present disclosure, a vehicle system isdisclosed. The system comprises a hitch assembly mounted on a vehicle, adisplay, and a controller. The controller is configured to access asaved configuration for the hitch assembly and display the savedconfiguration on the display. The controller is further configured toreceive a selection of the saved configuration and program acharacteristic of the hitch assembly based on the selection.

Embodiments of the first aspect of the invention can include any one ora combination of the following features:

-   -   the hitch assembly comprises a hitch ball in connection with a        hitch adapter, wherein the hitch adapter is in connection with        the vehicle;    -   the display comprises a user interface configured to display the        saved configuration;    -   the saved configuration comprises a plurality of configurations        for the hitch assembly accessed in a memory;    -   the saved configuration is stored in the memory based on a        previous record for the hitch assembly;    -   the saved configuration is saved in response to receiving a user        input identifying an instruction to save a configuration of the        hitch assembly;    -   at least one image sensor configured to capture image data in        communication with the controller;    -   the controller is further configured to detect a configuration        of the hitch assembly via an image processing routine processed        for the image data captured by the image sensor;    -   the image processing routine comprises an identification of a        proportion of a hitch ball and a position of the hitch ball in        the image data;    -   the controller is further configured to identify a coupler        configuration for a trailer; and    -   the controller is further configured to, based on the coupler        configuration, determine a connection compatibility between the        hitch assembly and the coupler.

According to another aspect of the present disclosure, a method foridentifying a hitch assembly in connection with a vehicle is disclosed.The method comprises capturing image data comprising the hitch assemblyand processing the image data identifying a configuration of the hitchassembly. The method further comprises identifying a location of acoupler of a trailer and controlling a navigation of the vehicle basedon the configuration of the hitch assembly and the location of thecoupler.

According to another aspect of the present disclosure, a vehicle systemfor a hitch assembly mounted on a vehicle and an imaging systemconfigured to capture image data comprising the hitch assembly. Thesystem further comprises a user interface comprising a display and acontroller. The controller is configured to detect the hitch assembly inthe image data and display a saved configuration on the display. Thecontroller is further configured to receive a selection of the savedconfiguration and control an automated navigation operation of thevehicle based on the configuration for the hitch assembly.

These and other aspects, objects, and features of the present disclosurewill be understood and appreciated by those skilled in the art uponstudying the following specification, claims, and appended drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 is a perspective view of a vehicle in an unhitched positionrelative to a trailer;

FIG. 2 is a diagram of a system according to an aspect of the disclosurefor assisting in aligning the vehicle with a trailer in a position forhitching the trailer to the vehicle;

FIG. 3 is an overhead schematic view of a vehicle during a step of thealignment sequence with the trailer;

FIG. 4 is a is an overhead schematic view of a vehicle during a step ofthe alignment sequence with the trailer;

FIG. 5 is a is a projected view of image data demonstrating an alignmentsequence with the trailer;

FIG. 6A is a side view of a vehicle demonstrating a hitch assemblymonitored by a field of view of a camera of an imaging system;

FIG. 6B is a side view of a vehicle demonstrating a hitch assemblymonitored by a field of view of a camera of an imaging system;

FIG. 7 is a projected view of image data displayed on a user interfacedemonstrating a hitch selection routine;

FIG. 8 is a projected view of image data displayed on a user interfacedemonstrating a hitch detection routine; and

FIG. 9 is a flow chart demonstrating a method for programming orselecting a hitch configuration for a vehicle in accordance with thedisclosure.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

For purposes of description herein, the terms “upper,” “lower,” “right,”“left,” “rear,” “front,” “vertical,” “horizontal,” “interior,”“exterior,” and derivatives thereof shall relate to the device asoriented in FIG. 1. However, it is to be understood that the device mayassume various alternative orientations, except where expresslyspecified to the contrary. It is also to be understood that the specificdevices and processes illustrated in the attached drawing, and describedin the following specification are simply exemplary embodiments of theinventive concepts defined in the appended claims. Hence, specificdimensions and other physical characteristics relating to theembodiments disclosed herein are not to be considered as limiting,unless the claims expressly state otherwise. Additionally, unlessotherwise specified, it is to be understood that discussion of aparticular feature or component extending in or along a given direction,or the like, does not mean that the feature or component follows astraight line or axis in such a direction or that it only extends insuch direction or on such a plane without other directional componentsor deviations, unless otherwise specified.

Referring generally to FIGS. 1-9, reference numeral 10 designates ahitch assistance system (also referred to as a “hitch assist” system)for a vehicle 12. In various embodiments, hitch assist system 10includes a controller 14 configured to acquire position data of acoupler 16 of a trailer 18. The controller 14 may be configured toderive a vehicle path 20 to align a hitch ball 22 a of the vehicle 12with the coupler 16. Deriving the vehicle path 20 may include a varietyof steps including detecting and compensating for a change in a couplerposition 24 in order to control the vehicle 12 to locate a hitchposition 26 aligned with the coupler 16. The vehicle path 20 maycomprise a plurality of segments 28, which may correspond to changes inthe operating direction or steering direction of the vehicle 12. Invarious embodiments, deriving the vehicle path 20 may include navigatingaround intervening objects or structures, operating over uneven terrain,following a desired path indicated by an operator or user U, etc.Accordingly, the disclosure may provide for the hitch assist system 10to provide for improved navigation of the vehicle 12 and/or interactionwith the coupler 16 such that trailer 18 may be effectively connected tothe vehicle 12 without complication.

In some embodiments, the hitch assist system 10 may be configured todetect and/or store a configuration of the hitch ball 22 a in connectionwith the vehicle 12. For example, as discussed further in reference toFIGS. 5-9, the connection of the vehicle 12 to the trailer 18 mayrequire a specific size for the hitch ball 22 a. Additionally, eachhitch ball 22 a may be connected to the vehicle 12 via a hitch adapter22 b or ball mount. The hitch adapter 22 b and the hitch ball 22 a maycorrespond to a hitch assembly 22. The hitch assembly 22 may connect thehitch ball 22 a to the vehicle in a variety of configurations. Inoperation, the user U of the system 10 may select the hitch ball 22 aand the hitch adapter 22 b via the HMI 66. Each of the combinations ofthe hitch ball 22 a and the hitch adapter 22 b may result in variationin the hitch position 26 and/or the height H_(b) of the hitch ball 22 a.A first configuration 30 a and a second configuration 30 b of the hitchassembly 22 are demonstrated in FIGS. 6A and 6B, respectively.

As is discussed further in reference to various embodiments, the hitchassist system 10 may be configured to detect a height H_(c) of thecoupler 16 and control the navigation of the vehicle 12 along thevehicle path 20. During the control of the vehicle 12, the hitch assistsystem 10 may identify whether the hitch ball 22 a is compatible withthe coupler 16. Additionally, the hitch assist system 10 may determinewhether the height H_(b) of the hitch ball 22 a is compatible with(e.g., below or less than) the height H_(c) of the coupler 16. In anexemplary embodiment, the controller 14 of the hitch assist system 10may be configured to detect and/or store the dimensions and thecompatibility of each of a plurality of hitch assemblies 22 to a varietyof trailers in order to improve an ease of use and accuracy of the hitchassist system 10.

With respect to the general operation of the hitch assist system 10, asillustrated in the system diagram of FIGS. 2-4, the hitch assist system10 includes various sensors and devices that obtain or otherwise providevehicle status-related information. This information includespositioning information from a positioning system 32, which may includea dead reckoning device 34 or, in addition or as an alternative, aglobal positioning system (GPS), to determine a coordinate location ofthe vehicle 12 based on the one or more locations of the devices withinthe positioning system 32. In particular, the dead reckoning device 34can establish and track the coordinate location of the vehicle 12 withina localized coordinate system 36 based at least on vehicle speed andsteering angle δ as shown in FIG. 3. Other vehicle information receivedby hitch assist system 10 may include a speed of the vehicle 12 from aspeed sensor 38 and a yaw rate of the vehicle 12 from a yaw rate sensor40. It is contemplated that in additional embodiments, a proximitysensor 42 or an array thereof, and other vehicle sensors and devices mayprovide sensor signals or other information, such as sequential imagesof the trailer 18, including the detected coupler 16, that thecontroller 14 of the hitch assist system 10 may process with variousroutines to determine the height H and position (e.g., based on thedistance D_(c) and angle α_(c)) of coupler 16.

As further shown in FIG. 2, one embodiment of the hitch assist system 10is in communication with the steering system 50 of vehicle 12. Thesteering system 50 may be a power assist steering system 50 including asteering motor 52 to operate the steered wheels 54 (FIG. 1) of thevehicle 12 for moving the vehicle 12 in such a manner that the vehicleyaw changes with the vehicle velocity and the steering angle S. In theillustrated embodiment, the power assist steering system 50 is anelectric power-assisted steering (“EPAS”) system including electricsteering motor 52 for turning the steered wheels 54 to a steering angleδ based on a steering command, whereby the steering angle δ may besensed by a steering angle sensor 56 of the power assist steering system50. The steering command may be provided by the hitch assist system 10for autonomously steering during a trailer hitch alignment maneuver andmay alternatively be provided manually via a rotational position (e.g.,steering wheel angle) of a steering wheel of vehicle 12.

In the illustrated embodiment, the steering wheel of the vehicle 12 ismechanically coupled with the steered wheels 54 of the vehicle 12, suchthat the steering wheel moves in concert with steered wheels 54,preventing manual intervention with the steering wheel during autonomoussteering. More specifically, a torque sensor 58 is provided on the powerassist steering system 50 that senses torque on the steering wheel thatis not expected from autonomous control of the steering wheel andtherefore indicative of manual intervention. In this configuration, thehitch assist system 10 may alert the driver to discontinue manualintervention with the steering wheel and/or discontinue autonomoussteering. In alternative embodiments, some vehicles have a power assiststeering system 50 that allows a steering wheel to be partiallydecoupled from movement of the steered wheels 54 of such a vehicle.

With continued reference to FIG. 2, the power assist steering system 50provides the controller 14 of the hitch assist system 10 withinformation relating to a rotational position of steered wheels 54 ofthe vehicle 12, including a steering angle δ. The controller 14 in theillustrated embodiment processes the current steering angle, in additionto other vehicle 12 conditions to guide the vehicle 12 along the desiredpath 20 (FIG. 3). It is conceivable that the hitch assist system 10, inadditional embodiments, may be an integrated component of the powerassist steering system 50. For example, the power assist steering system50 may include a hitch assist algorithm for generating vehicle steeringinformation and commands as a function of all or a portion ofinformation received from an imaging system 60, the power assiststeering system 50, a vehicle brake control system 62, a powertraincontrol system 64, and other vehicle sensors and devices, as well as ahuman-machine interface (“HMI”) 66, as discussed further below.

As also illustrated in FIG. 2, the vehicle brake control system 62 mayalso communicate with the controller 14 to provide the hitch assistsystem 10 with braking information, such as vehicle wheel speed, and toreceive braking commands from the controller 14. The brake controlsystem 62 may be configured to control service brakes 62 a and a parkingbrake 62 b. The parking brake 62 b may correspond to an electronicparking brake system that may be in communication with the controller14. Accordingly in operation, the controller 14 may be configured tocontrol the brakes 62 a and 62 b as well as detect vehicle speedinformation, which may be determined from individual wheel speed sensorsmonitored by the brake control system 62. Vehicle speed may also bedetermined from the powertrain control system 64, the speed sensor 38,and/or the positioning system 32, among other conceivable means. In someembodiments, individual wheel speeds can also be used to determine avehicle yaw rate, which can be provided to the hitch assist system 10 inthe alternative or in addition to the vehicle yaw rate sensor 40.

The hitch assist system 10 can further provide vehicle brakinginformation to the brake control system 62 for allowing the hitch assistsystem 10 to control braking of the vehicle 12 during backing of thetrailer 18. For example, the hitch assist system 10, in someembodiments, may regulate speed of the vehicle 12 during alignment ofthe vehicle 12 with the coupler 16 of trailer 18, which can reduce thepotential for a collision with trailer 18, and can bring vehicle 12 to acomplete stop at a determined endpoint 70 of the path 20. It isdisclosed herein that the hitch assist system 10 can additionally oralternatively issue an alert signal corresponding to a notification ofan actual, impending, and/or anticipated collision with a portion oftrailer 18. The powertrain control system 64, as shown in the embodimentillustrated in FIG. 2, may also interact with the hitch assist system 10for regulating speed and acceleration of the vehicle 12 during partialor autonomous alignment with trailer 18. As mentioned above, regulationof the speed of the vehicle 12 may be advantageous to prevent collisionwith trailer 18.

As previously discussed, the hitch assist system 10 may communicate withhuman-machine interface (“HMI”) 66 of the vehicle 12. The HMI 66 mayinclude a vehicle display 72, such as a center-stack mounted navigationor entertainment display (FIG. 1). HMI 66 further includes an inputdevice, which can be implemented by configuring display 72 as a portionof a touchscreen 74 with circuitry 76 to receive an input correspondingwith a location over display 72. Other forms of input, including one ormore joysticks, digital input pads, or the like, can be used in place orin addition to touchscreen 74. Further, the hitch assist system 10 maycommunicate via wireless communication with another embodiment of theHMI 66, such as with one or more handheld or portable devices 80 (FIG.1), including one or more smartphones. The portable device 80 may alsoinclude the display 72 for displaying one or more images and otherinformation to a user U. For instance, the portable device 80 maydisplay one or more images of the trailer 18 on the display 72 and maybe further configured to receive remote user inputs via touchscreencircuitry 76. In addition, the portable device 80 may provide feedbackinformation, such as visual, audible, and tactile alerts.

In some embodiments, the hitch assist system 10 may further be incommunication with one or more indicator devices 78. The indicatordevices 78 may correspond to conventional vehicle indicators, such as avehicle horn 78 a, lights 78 b, a speaker system 78 c, vehicleaccessories 78 d, etc. In some embodiments, the indicator devices 78 mayfurther include one or more accessories 78 d, which may correspond tocommunication devices, remote controls, and a variety of devices thatmay provide for status and operational feedback between the user U andthe vehicle 12. For example, in some embodiments, the HMI 66, thedisplay 72, and the touchscreen 74 may be controlled by the controller14 to provide status updates identifying the operation or receivinginstructions or feedback to control the hitch assist system 10.Additionally, in some embodiments, the portable device 80 may be incommunication with the controller 14 and configured to display orotherwise indicate one or more alerts or messages related to theoperation of the hitch assist system 10.

Still referring to the embodiment shown in FIG. 2, the controller 14 isconfigured with a microprocessor 82 to process logic and routines storedin memory 84 that receive information from the above-described sensorsand vehicle systems, including the imaging system 60, the power assiststeering system 50, the vehicle brake control system 62, the powertraincontrol system 64, and other vehicle sensors and devices. The controller14 may generate vehicle steering information and commands as a functionof all or a portion of the information received. Thereafter, the vehiclesteering information and commands may be provided to the power assiststeering system 50 for affecting steering of the vehicle 12 to achieve acommanded path 20 (FIG. 3) of travel for alignment with the coupler 16of trailer 18. The controller 14 may include the microprocessor 82and/or other analog and/or digital circuitry for processing one or moreroutines. Also, the controller 14 may include the memory 84 for storingone or more routines, including an image processing routine 86 and/orhitch detection routine, a path derivation routine 88, and an operatingroutine 90.

It should be appreciated that the controller 14 may be a stand-alonededicated controller or may be a shared controller integrated with othercontrol functions, such as integrated with a vehicle sensor system, thepower assist steering system 50, and other conceivable onboard oroff-board vehicle control systems. It should further be appreciated thatthe image processing routine 86 may be carried out by a dedicatedprocessor, for example, within a stand-alone imaging system for vehicle12 that can output the results of its image processing to othercomponents and systems of vehicle 12, including microprocessor 82.Further, any system, computer, processor, or the like, that completesimage processing functionality, such as that described herein, may bereferred to herein as an “image processor” regardless of otherfunctionality it may also implement (including simultaneously withexecuting image processing routine 86).

Hitch assist system 10 may also incorporate the imaging system 60 thatincludes one or more exterior cameras 60 a-60 d. Examples of exteriorcameras are illustrated in FIG. 4 and include rear camera 60 a, centerhigh-mount stop light (CHMSL) camera 60 b, and side-view cameras 60 cand 60 d, although other arrangements including additional oralternative cameras are possible. In one example, imaging system 60 caninclude rear camera 60 a alone or can be configured such that system 10utilizes only rear camera 60 a in a vehicle with multiple exteriorcameras. In another example, the various cameras 60 a-60 d included inimaging system 60 can be positioned to generally overlap in theirrespective fields of view, which in the depicted arrangement includefields of view 92 a, 92 b, 92 c, and 92 d to correspond with rear camera60 a, center high-mount stop light (CHMSL) camera 60 b, and side-viewcameras 60 c and 60 d, respectively. In this manner, image data from twoor more of the cameras 60 a-60 d can be combined in image processingroutine 86, or in another dedicated image processor within imagingsystem 60, into a single image.

As an example of combining image data from multiple cameras, the imagedata can be used to derive stereoscopic image data that can be used toreconstruct a three-dimensional scene of the area or areas withinoverlapped areas of the various fields of view 92 a, 92 b, 92 c, and 92d, including any objects (obstacles or coupler 16, for example) therein.In an embodiment, the use of two images including the same object can beused to determine a location of the object relative to the two imagesources, given a known spatial relationship between the image sources.In this respect, the image processing routine 86 can use knownprogramming and/or functionality to identify an object within image datafrom the various cameras 60 a, 60 b, 60 c, and 60 d within imagingsystem 60. In either example, the image processing routine 86 caninclude information related to the positioning of any cameras 60 a, 60b, 60 c, and 60 d present on vehicle 12 or utilized by system 10,including relative to a center 96 (FIG. 1) of vehicle 12, for example,such that the positions of cameras 60 a, 60 b, 60 c, and 60 d relativeto center 96 and/or to each other can be used for object positioningcalculations and to result in object position data relative to thecenter 96 of vehicle 12, for example, or other features of vehicle 12,such as hitch ball 22 a (FIG. 1), with known positions relative tocenter 96 of the vehicle 12.

The image processing routine 86 can be specifically programmed orotherwise configured to locate coupler 16 within image data. In oneexample, the image processing routine 86 can identify the coupler 16within the image data based on stored or otherwise known visualcharacteristics of coupler 16 or hitches in general. In anotherembodiment, a marker in the form of a sticker, or the like, may beaffixed with trailer 18 in a specified position relative to coupler 16in a manner similar to that which is described in commonly-assigned U.S.Pat. No. 9,102,271, the entire disclosure of which is incorporated byreference herein. In such an embodiment, image processing routine 86 maybe programmed with identifying characteristics of the marker forlocation in image data, as well as the positioning of coupler 16relative to such a marker so that the position 24 of coupler 16 can bedetermined based on the marker location.

Additionally or alternatively, controller 14 may seek confirmation ofthe determined coupler 16, via a prompt on touchscreen 74. If thecoupler 16 determination is not confirmed, further image processing maybe provided, or user-adjustment of the position 24 of coupler 16 may befacilitated, either using touchscreen 74 or another input to allow theuser U to move the depicted position 24 of coupler 16 on touchscreen 74,which controller 14 uses to adjust the determination of position 24 ofcoupler 16 with respect to vehicle 12 based on the above-described useof image data. Alternatively, the user U can visually determine theposition 24 of coupler 16 within an image presented on HMI 66 and canprovide a touch input in a manner similar to that which is described incommonly-assigned U.S. Pat. No. 10,266,023, the entire disclosure ofwhich is incorporated by reference herein. The image processing routine86 can then correlate the location of the touch input with thecoordinate system 36 applied to image data shown on the display 72,which may be depicted as shown in FIG. 3.

As shown in FIG. 3, the image processing routine 86 and operatingroutine 90 may be used in conjunction with each other to determine thepath 20 along which hitch assist system 10 can guide vehicle 12 to alignhitch ball 22 a and coupler 16 of trailer 18. In the example shown, aninitial position of vehicle 12 relative to trailer 18 may be such thatcoupler 16 is only in the field of view 92 c of side-view camera 60 c,with vehicle 12 being positioned laterally from trailer 18 but withcoupler 16 being almost longitudinally aligned with hitch ball 22 a. Inthis manner, upon initiation of hitch assist system 10, such as by userinput on touchscreen 74, for example, image processing routine 86 canidentify coupler 16 within the image data of camera 60 c and estimatethe position 24 of coupler 16 relative to hitch ball 22 a. The position24 of the coupler 16 may be identified by the system 10 using the imagedata in accordance by receiving focal length information within imagedata to determine a distance D_(c) to coupler 16 and an angle α_(c) ofoffset between coupler 16 and the longitudinal axis of vehicle 12. Thisinformation can then be used in light of the position 24 of coupler 16within the field of view 92 c of the image data to determine or estimatethe height H_(c) of coupler 16. Once the positioning D_(c), ac ofcoupler 16 has been determined and, optionally, confirmed by the user U,the controller 14 can take control of at least the vehicle steeringsystem 50 to control the movement of vehicle 12 along the desired path20 to align the hitch position 26 of the vehicle hitch ball 22 a withcoupler 16.

Continuing with reference to FIGS. 3 and 4 with additional reference toFIG. 2, controller 14, having estimated the positioning D_(c), α_(c) ofcoupler 16, as discussed above, can, in one example, execute pathderivation routine 88 to determine vehicle path 20 to align the vehiclehitch ball 22 a with coupler 16. In particular, controller 14 can havestored in memory 84 various characteristics of vehicle 12, including thewheelbase W, the distance from the rear axle to the hitch ball 22 a,which is referred to herein as the drawbar length L, as well as themaximum angle to which the steered wheels 54 can be turned δ_(max). Asshown, the wheelbase W and the current steering angle δ can be used todetermine a corresponding turning radius p for vehicle 12 according tothe equation:

$\begin{matrix}{{\rho = \frac{1}{W\;\tan\;\delta}},} & (1)\end{matrix}$in which the wheelbase W is fixed and the steering angle δ can becontrolled by controller 14 by communication with steering system 50, asdiscussed above. In this manner, when the maximum steering angle δ_(max)is known, the smallest possible value for the turning radius ρ_(min) isdetermined as:

$\begin{matrix}{\rho_{\min} = {\frac{1}{W\;\tan\;\delta_{\max}}.}} & (2)\end{matrix}$

Path derivation routine 88 can be programmed to derive vehicle path 20to align a known location of the vehicle hitch ball 22 a with theestimated position 24 of coupler 16 that takes into account thedetermined minimum turning radius ρ_(min) to allow path 20 to use theminimum amount of space and maneuvers. In this manner, path derivationroutine 88 can use the position of vehicle 12, which can be based on thecenter 96 of vehicle 12, a location along the rear axle, the location ofthe dead reckoning device 34, or another known location on thecoordinate system 36, to determine both a lateral distance to thecoupler 16 and a forward or rearward distance to coupler 16 and derive apath 20 that achieves the needed lateral and forward-backward movementof vehicle 12 within the limitations of steering system 50. Thederivation of path 20 further takes into account the positioning ofhitch ball 22 a, based on length L, relative to the tracked location ofvehicle 12 (which may correspond with the center 96 of mass of vehicle12, the location of a GPS receiver, or another specified, known area) todetermine the needed positioning of vehicle 12 to align hitch ball 22 awith coupler 16.

As discussed above, hitch assist system 10 can provide image data toimage processing routine 86 that can be used by image processing routine86 (by the process described above or by other available processes) todetermine the height H_(b) of hitch ball 22 a (i.e., a verticalcomponent of the data including the position 24 of coupler 16. The imagedata may be captured by one or more of the cameras 60 a-60 d of theimaging system 60. Further, hitch assist system 10 can have stored inmemory 84 or can otherwise determine the height H_(b) of hitch ball 22a. In one example, during an initial setup routine for hitch assistsystem 10, a user U can be prompted to install hitch ball 22 a by way ofassembling a ball mount including hitch ball 22 a with a receiverpositioned on the rear of vehicle 12. The user U can then be asked tomeasure the height H_(b) of the hitch ball 22 a (such as to the top orcenter thereof) and to enter that measurement into memory 84 by way ofHMI 66, for example. In this manner, a number of different heightmeasurements for a plurality of hitch balls used in connection with theparticular vehicle 12 can be stored in memory 84 and can be selected bythe user U. In some embodiments, hitch ball 22 a may be within the fieldof view 92 a of rear camera 60 a such that image data can be processedto determine the height H_(b) of hitch ball 22 a on a real-time oron-demand basis.

Referring now to FIGS. 5, 6A, and 6B, as previously discussed, the hitchassist system 10 may be configured to detect and/or store aconfiguration of the hitch ball 22 a in connection with the vehicle 12.In some embodiments, the system 10 may be configured to store aplurality of the configurations 30 of the hitch assemblies 22identifying a diameter and connection configuration of the hitch ball 22a via the hitch adapter 22 b or ball mount. The hitch assembly 22 mayconnect the hitch ball 22 a to the vehicle in a variety ofconfigurations. In operation, the user U of the system 10 may select thehitch ball 22 a and the hitch adapter 22 b via the HMI 66 furtherdiscussed in reference to FIGS. 7 and 8. Each of the combinations mayresult in variation in the hitch position 26 and/or the height H_(b) ofthe hitch ball 22 a. A first configuration 30 a and a secondconfiguration 30 b of the hitch assembly 22 are demonstrated in FIGS. 6Aand 6B, respectively.

As is discussed further in reference to various embodiments, the hitchassist system 10 may be configured to detect a height H_(c) of thecoupler 16 and control the navigation of the vehicle 12 along thevehicle path 20. During the control of the vehicle 12, the system 10 mayidentify whether the hitch ball 22 a is compatible with the coupler 16.Additionally, the system 10 may determine whether the height H_(b) ofthe hitch ball 22 a is compatible with (e.g., below or less than) theheight H_(c) of the coupler 16. In an exemplary embodiment, thecontroller 14 of the hitch assist system 10 may be configured to detectand/or store the dimensions and the compatibility of each of a pluralityof hitch assemblies 22 to a variety of trailers in order to improve anease of use and accuracy of the system 10. In some embodiments, thehitch assist system 10 may further be configured to detect a connectionconfiguration of the coupler 16 of the trailer 18.

Referring to FIG. 5, the controller 14 may be configured to process theimage data received from the imaging system 60 and display one or moreof the fields of view 92 on the display 72 of the vehicle 12. Based onthe image data received from the imaging system 60, the controller 14may be configured to identify the position 24 of the coupler 16 as wellas the connection configuration 94 of the trailer 18. As demonstrated,in response to the activation of the trailer connection routine, thecontroller 14 may present a plurality of connection configurations 94for the trailer 18 on the HMI 66. Accordingly, the connectionconfigurations 94 for the trailer 18 may be detected or identified bythe image processing routine 86 based on stored or otherwise knownvisual characteristics of coupler 16, the trailer 18, or hitches ingeneral.

Referring now to FIGS. 6A, 6B, 7, and 8 the trailer connection routinemay continue to detect or prompt the user U to identify theconfiguration 30 of the hitch assembly 22. As shown in FIGS. 6A and 6B,the imaging system 60 may be configured to detect the hitch ball 22 a ina plurality of configurations 30, which may include a firstconfiguration 30 a and a second configuration 30 b. In the firstconfiguration 30 a, the height H_(b) of the hitch ball 22 a may begreater that the height H_(b) in the second configuration 30 b.Additionally, the diameter of the hitch ball 22 a and the hitch position26 may vary in each of the configurations 30. Identifying suchdifferences in the configurations 30 may be important to ensure that thehitch assist system 10 may accurately determine the height H_(b) of thehitch ball 22 a and the compatibility between the hitch ball 22 a andthe trailer 18.

The disclosure provides for the controller 14 to detect theconfiguration 30 via the image processing routine 86 and/or prompt theuser U to identify the configuration 30 on the HMI 66. Based on theconfiguration 30 of the hitch assembly 22 as well as the connectionconfiguration 94 of the trailer 18, the controller 14 may identify theheight H_(b) and position of the hitch ball 22 a as well as thecompatibility of the hitch ball 22 a with the trailer 18. Accordingly,the controller 14 may be configured to identify a compatibility of thehitch ball 22 a with the trailer 18 and adjust a location of the hitchball 22 a to maintain accuracy of the path derivation routine 88. Thoughthe disclosure is discussed in reference to specific embodimentsdepicted in the accompanying figures, the system 10 may be implementedto suit a variety of applications without departing from the spirit ofthe disclosure.

As shown in FIG. 7, the display 72 of the HMI 66 is shown demonstratinga manual selection for the configuration 30 of the hitch assembly 22. Asillustrated, the plurality of configurations 30 are shown on the display72 prompting the user U to identify the current configuration. Each ofthe configurations 30 may be stored in the memory 84 after an initialsetup. For example, upon initial setup for each of the configurations30, the controller 14 may prompt the user U to enter the details of theconfiguration via an add configuration option 96. In this way, the hitchassist system 10 may be configured to prompt the user U to make aselection identifying the hitch assembly 22 or the dimensions of thehitch assembly in response to the initialization of the hitch assistroutine.

As demonstrated, each of the configurations 30 of the hitch assembly 22may comprise an identification of the hitch adapter 22 b as well as thehitch ball 22 a. In this way, the controller 14 may identify changes inthe configuration 30 of the hitch assembly 22 and compare theconfiguration 30 to the connection configuration 94 of the trailer 18.For example, the controller may compare the size of the hitch ball 22 ato the size of the coupler 16 to ensure that the sizes are compatible.Each of the connection configurations 94 may comprise a name oridentifier for the trailer 18 as well as information regarding thediameter of the coupler 16. In this way, the controller 14 may comparethe size of the hitch ball 22 a with the connection configuration 94 ofthe trailer 18 to identify the compatibility of the coupler 16 of thetrailer 18 with the hitch assembly 22.

Referring now to FIG. 8, in some embodiments, the controller 14 may beconfigured to detect the configuration 30 of the hitch assembly 22. Forexample, upon initiation of hitch assist system 10, such as by userinput on touchscreen 74 of the HMI 66, the image processing routine 86may identify the configuration 30 of the hitch assembly 22 in the imagedata in the first field of view 92 a of the camera 60 a. As previouslydiscussed, based on the image data, the controller 14 may identify therelative hitch position 26 and proportions of the hitch ball 22 a in thefield of view 92 a. In this way, the controller 14 may automaticallyidentify the configuration 30 of the hitch assembly 22 and display theconfiguration 30 on the display 72 of the HMI 66.

Once the configuration 30 of the hitch assembly 22 is identified, thecontroller 14 may further prompt the user U to verify the configuration30. As demonstrated in FIG. 8, the controller 14 may display each of aplurality of configurations 30 and highlight a detected configuration102 for selection or confirmation by the user U. Once the selection ordetection of the configuration 30 of the hitch assembly 22 is complete,the controller 14 may initiate the path derivation routine 88 and theoperating routine 90. In this way, the controller 14 may ensure that theoperation of the hitch assist system 10 is user friendly and intuitive.

Referring now to FIG. 9, a flow chart demonstrating a method 110 for theselection of the configuration 30 for the hitch assembly 22 is shown. Inoperation, the method 110 begins in response to the initialization of ahitch connection routine, which may be selected by the user U via theHMI 66 (112). The method 110 may continue by prompting the user U toselect a hitch configuration on the display 72 (114). The controller 14may then prompt the user U to identify whether the hitch assembly 22 isa saved configuration or a new configuration as described in decisionstep 116. In response to the user identifying that the configuration 30was previously saved, the controller 14 may continue to step 118prompting the user U to select the configuration 30 for the hitchassembly 22 on the HMI 66. In response to receiving a selection of theconfiguration 30, the controller 14 may continue to perform the hitchassist routine by processing the path derivation routine 88 and theoperating routine 90 (120).

If a new configuration (e.g., the add configuration option 96) isselected in step 116, the controller 14 may then continue to detect orreceive the configuration 30 of the hitch assembly 22 (122). Aspreviously discussed, the controller 14 may detect the configuration 30of the hitch assembly 22 via the image processing routine 86 byprocessing the image data in the first field of view 92 a of the camera60 a. Additionally, the controller 14 may be configured to receive aninput from the user U identifying the configuration 30 of the hitchassembly 22 via the HMI 66 in step 122. Once identified, the controller14 may utilize the configuration 30 of the hitch assembly 22 to performthe hitch assist routine (124). In this way, the controller 14 may beconfigured to process and complete the path derivation routine 88 andthe operating routine 90 for various configurations of the hitchassembly 22 and the coupler 16 of the trailer 18.

Following the completion of the hitch assist routine in step 124, thecontroller 14 may prompt the user U via the HMI to specify whether ornot to save the new configuration from step 122 (126). The controller 14may then determine if the user U decides to save the new configurationbased on an input received by the HMI 66 (128). If the new configurationis saved in step 128, the controller 14 may save the new configurationto the memory 84 (130). Following steps 128 and 130, the method 110 maycontinue by completing the hitch assist routine in step 132.Accordingly, the system 10 may provide for improved ease of operation ofthe vehicle 12 in detecting the hitch assembly 22 and connecting thevehicle 12 to the trailer 18.

It is to be understood that variations and modifications can be made onthe aforementioned structure without departing from the concepts of thepresent disclosure, and further it is to be understood that suchconcepts are intended to be covered by the following claims unless theseclaims by their language expressly state otherwise.

For purposes of this disclosure, the term “coupled” (in all of itsforms, couple, coupling, coupled, etc.) generally means the joining oftwo components (electrical or mechanical) directly or indirectly to oneanother. Such joining may be stationary in nature or movable in nature.Such joining may be achieved with the two components (electrical ormechanical) and any additional intermediate members being integrallyformed as a single unitary body with one another or with the twocomponents. Such joining may be permanent in nature or may be removableor releasable in nature unless otherwise stated.

It is also important to note that the construction and arrangement ofthe elements of the disclosure as shown in the exemplary embodiments isillustrative only. Although only a few embodiments of the presentinnovations have been described in detail in this disclosure, thoseskilled in the art who review this disclosure will readily appreciatethat many modifications are possible (e.g., variations in sizes,dimensions, structures, shapes and proportions of the various elements,values of parameters, mounting arrangements, use of materials, colors,orientations, etc.) without materially departing from the novelteachings and advantages of the subject matter recited. For example,elements shown as integrally formed may be constructed of multiple partsor elements shown as multiple parts may be integrally formed, theoperation of the interfaces may be reversed or otherwise varied, thelength or width of the structures and/or members or connector or otherelements of the system may be varied, the nature or number of adjustmentpositions provided between the elements may be varied. It should benoted that the elements and/or assemblies of the system may beconstructed from any of a wide variety of materials that providesufficient strength or durability, in any of a wide variety of colors,textures, and combinations. Accordingly, all such modifications areintended to be included within the scope of the present innovations.Other substitutions, modifications, changes, and omissions may be madein the design, operating conditions, and arrangement of the desired andother exemplary embodiments without departing from the spirit of thepresent innovations.

It will be understood that any described processes or steps withindescribed processes may be combined with other disclosed processes orsteps to form structures within the scope of the present disclosure. Theexemplary structures and processes disclosed herein are for illustrativepurposes and are not to be construed as limiting.

What is claimed is:
 1. A vehicle system, comprising: a hitch assemblymounted on a vehicle; a display; and a controller that: stores aplurality of trailer selections as a plurality of saved configurations,wherein each of the saved configurations identify a hitch sizecompatibility of a trailer corresponding to each of the trailerselections; accesses a plurality of saved configurations for the hitchassembly; displays the saved configurations on the display; receives aselection identifying one of the saved configurations; and programs acharacteristic of the hitch assembly based on the selection.
 2. Thesystem according to claim 1, wherein the hitch assembly comprises ahitch ball in connection with a hitch adapter, wherein the hitch adapteris in connection with the vehicle.
 3. The system according to claim 1,wherein the display comprises a user interface configured to display thesaved configurations.
 4. The system according to claim 1, wherein thesaved configuration comprises a plurality of configurations for thehitch assembly accessed in a memory.
 5. The system according to claim 1,wherein the saved configurations are stored in the memory based on aprevious record for the hitch assembly.
 6. The system according to claim5, wherein the saved configurations are saved in response to receiving auser input identifying an instruction to save a configuration of thehitch assembly.
 7. The system according to claim 1, further comprising:at least one image sensor configured to capture image data incommunication with the controller.
 8. The system according to claim 7,wherein the controller further: detects a configuration of the hitchassembly via an image processing routine processed for the image datacaptured by the image sensor.
 9. The system according to claim 8,wherein the image processing routine comprises an identification of aproportion of a hitch ball and a position of the hitch ball in the imagedata.
 10. The system according to claim 1, wherein the controllerfurther: identifies a coupler configuration for a coupler of a trailer;and based on the coupler configuration, determines a connectioncompatibility between the hitch assembly and the coupler of the trailer.11. The system according to claim 10, wherein the connectioncompatibility comprises a hitch ball diameter of a hitch ball of thehitch assembly and connection diameter of the coupler.
 12. The systemaccording to claim 1, wherein the plurality of saved configurations arestored in the memory in response to entries received via the userinterface, wherein the entries identify the hitch size compatibility foreach of the trailers corresponding of the saved configurations.
 13. Thesystem according to claim 1, wherein the hitch size compatibilitycomprises a hitch ball size requirement for each of the trailers of thesaved configurations.